All Hypertrieve database transactions are written to a transaction log file. If the Hypertrieve database is corrupted, this will be detected by Meridian at startup time. The log file will then be replayed to rebuild the database. Depending on the length of the log file, this process can be time-consuming. If the Hypertrieve database gets corrupted, for example, when the server is switched off without a proper shutdown procedure, Meridian tries to recover the database automatically when the server reboots. If such an event has happened, information is written to the Windows event log (application log). In this case all data created until the moment of database corruption is maintained.
Related concepts
Understanding database recovery
Understanding level 2 recovery
Understanding level 3 recovery
Related tasks